fix(examples): use correct genericViewportDisplaySetMetadataProvider name - #2779
Conversation
…name genericViewportShowcase called utilities.genericViewportDataSetMetadataProvider, which doesn't exist on the core utilities export and throws at runtime.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughSwitches metadata registration in the ChangesGeneric Viewport Showcase Metadata Provider Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
genericViewportShowcasecalledutilities.genericViewportDataSetMetadataProvider, which doesn't exist on the coreutilitiesexport (the real export isgenericViewportDisplaySetMetadataProvider), causing a runtime error/no-op when the example registers display-set metadata.Test plan
build-all-examples-cli.js --build --fromRoot --packages core,tools) — compiles with no warnings (previously emittedESModulesLinkingWarningfor this export)..static-exampleslocally and loadedgenericViewportShowcase.html.Summary by CodeRabbit